Task: Develop system verification plan
Development of the verification plan for the Systems integration level, describing the verification tools, methods and environment with pass and fail criteria.
Purpose

To describe the verification tools, methods and environment with pass and fail criteria to be applied at the System integration level.

Relationships
Main Description

ISO 26262, vol 8, clause 9 defines the guidance for generic aspects of verification planning which should be followed.

In order to detect systematic faults within the implementation during systems integration, various test methods must be selected that cover a variety of aspects of test and verification.

The selection of the application feasible methods are detailed in the steps section.

Steps
Select methods for the Correctness of implementation of system design specification, technical and functional safety requirements

To ensure the correctness of implementation of functional safety requirements the following types of test are all highly recommended at all ASIL levels

Requirements-based test, this highly recommended for items of any ASIL. level

Fault injection test, this is highly recommended for items of ASIL of C or D and recommended for items with an ASIL of A or B

Back to back tests, this is highly recommended for items of ASIL of D and recommended for items of ASIL of B or C with an unbiased opinion on its usage for items of ASIL A

Requirements based testing is used to test against functional and non-functional (quality of service) requirements.

Fault injection test uses special means to introduce faults into the item. This can be done within the item via a special test interface or specially prepared elements or communication devices. The method is often used to improve the test coverage of the safety requirements, because during normal operation safety mechanisms are not invoked

Back to back testing compares the outputs of the test object to the outputs of a simulation model when both are subjected to the same set of inputs. This technique is common when using model based testing techniques, comparing specification scenarios captured in sequence diagrams to the actual outputs from the code.



This summary is based upon "Table 10 Correct implementation of functional safety and technical safety requirements at the systems level", located in ISO 26262, vol 4, clause 8.4.4.2.1 .

Select methods for the correctness of functional performance, accuracy and timing of safety mechanisms (A), (B), (C), D

These tests are required for items of ASIL D and recommend for items of ASIL A, B or C

Please refer to Table 11 Correct functional performance, accuracy and timing of the safety mechanisms at the systems level located in ISO 26262, vol 4, clause 8.4.4.2.3, for details of recommendations for these test types against ASIL. In summary the types of test mentioned are.

Back to back tests

Performance tests

Both types of test are recommended for  for items of ASIL B or C and highly recommended for items of ASIL D,  with an unbiased opinion on there usage for items of ASIL A

Back to back test compare the output from the item being tested to the output of a simulation model to the same set of inputs. This is to detect the difference between the model and implementation. This is a common technique in model based development for software.

Performance test can verify that the safety mechanisms in the system respond according the to the intended quality of service requirements.

Select methods for the consistency and correctness of implementation of external and internal interfaces

To ensure the consistency and correctness of implementation of external and internal interfaces the following types of test recommended, depending upon the ASIL level of the item being tested. See ISO 26262 vol 4 clause 8.4.4.2.4

Consistent and correct implementation of external and internal interfaces at the system level


 

This table/figure is taken from ISO 26262:2011-8.4.3.2.4 © ISO 2011 – All rights reserved. Reproduced with the permission of ANSI on behalf of ISO.

Copyright ISO 2011. All rights reserved. Reproduced with permission of ANSI.

Select methods for the effectiveness of diagnostic failure coverage of safety mechanisms at system level (A), (B), C, D

These tests are required for items of ASIL C or D and recommend for items of ASIL A or B

To ensure the Effectiveness of diagnostic failure coverage of safety mechanisms at system level the following types of test are recommended depending upon the ASIL level of the item being developed. See ISO 26262 vol 4 clause 8.4.4.2.5

Effectiveness of a safety mechanism's failure coverage at the system level

This table/figure is taken from ISO 26262:2011-8.4.3.2.5 © ISO 2011 – All rights reserved. Reproduced with the permission of ANSI on behalf of ISO.

Copyright ISO 2011. All rights reserved. Reproduced with permission of ANSI.



Select methods for the level of robustness (A), (B), C, D

These tests are required for items of ASIL C or D and recommended for items of ASIL A or B

To determine the test required to ensure the Level of robustness of the item, please refer to "Table 19-Level of robustness at the vehicle level" located in ISO 26262, vol 4, clause 8.4.4.2.6, in summary the tests to be carried out are

Resource usage test  is highly recommended items of ASIL C or D and recommended for items of ASIL B, with an unbiased opinion on its usage for items of ASIL A

Stress test is highly recommended items of ASIL C or D and recommended for items of ASIL B, with an unbiased opinion on its usage for items of ASIL A

Test for interference resistance and robustness under certain environmental condition is highly recommended for items of all ASIL levels 

At the item level, lab cars or prototypes are usually employed to create a dynamic environment for the tests. The focus of these test are items such as power consumption or bus loading.

Stress tests are used to verify the correct operation of the item under high operational loads or extreme environmental conditions.

A test for interference resistance and robustness under certain environmental conditions is a special case of stress testing. This includes EMC and ESD tests.


Properties
Multiple Occurrences
Event Driven
Ongoing
Optional
PlannedYes
Repeatable
Key Considerations

Practices applicable to help develop the System Verification plan are

More Information